chore: release 1.17.1 #1677
chore: release 1.17.1 #1677
Conversation
| version = "0.18.0" | ||
| version = "0.18.1" |
There was a problem hiding this comment.
Since these are unstable crates anyway should we just bump the minor version? In the next release we would be bumping to 0.19.0 anyway.
There was a problem hiding this comment.
I like the idea of trying to stick to semver for all of the crates, because I think that's easier to reason about.
E.g. "we follow semver for all of the crates that we publish" rather than "we follow semver for the primary crate that we publish and but not for published, non-primary crates"
There was a problem hiding this comment.
Although I admit that figuring out whether things should be minor/patch bumps is currently rather tedious, the solution I would push for is automating version bumps through the conventional commit parsing.
Description of changes:
updates s2n-quic to 1.17.1
Call-outs:
1.17.0 was not released. I don't expect there to be any particular complications with that, but please comment if you see some issue with that.
Testing:
CI should pass
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.